An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hey people, I would like to know how long it usually takes a first-time app publisher to get their app reviewed for the first time. I submitted my app on 20.07.22026 and am still stuck waiting for a review status, and today is the 8th day in the queue. App is submitted from account 6783418786. • Is there a specific reason for this extended hold? • Is any action required from my side? • When can I expect the review to proceed? Thank you very much for your time and assistance.

Hello, Our first app submission has been in "Waiting for Review" since July 22 with no status change (6 days). App name: Randevu Sıram Bundle ID: com.siram.app Version / Build: 1.0 (19) Submission ID: 8499a973-8efa-4066-bb5c-e28847a07e34 Date submitted: July 22, 2026, 12:21 PM Support Case ID: 20000120821151 This is our first submission from a new developer account. The App Review Information section includes a demo account for the business panel, and the customer side is usable without login. We contacted App Review Support on July 26 (case above) but have not received a reply yet. Any information about the status would be appreciated. Thank you.

I submitted my iOS app (Apple ID 6792378109) on 07/18/26. It has been in "Waiting for Review" for 10 days now. I did reach out to Developer Support via email on 07/26 (Case ID 20000120078126) and haven't received a reply as yet. This is a first time app submission. If the following is no longer true, it should probably be updated or changed to reflect the current situation: On average, 50 percent of apps are reviewed in 24 hours and over 90 percent are reviewed in 48 hours. Once we've completed the review, your app's status will be updated and you will be notified. in order to manage expectations. If there's an ongoing technical issue, knowing that's the cause of delays is preferable to silence. In any event, if someone is able to shake my review loose, I'd appreciate it!

I submitted my IOS app (Apple ID 6783073058) on 2026-07-21. The submission confirmation email says: On average, 50 percent of apps are reviewed in 24 hours and over 90 percent are reviewed in 48 hours. Once we've completed the review, your app's status will be updated and you will be notified. After 6 days still Waiting for Review, I asked Claude if there was any way to check on the status. He suggested opening a support ticket. When I filed 20000121192005 I was given the option to call or email, so I opted for a call. Immediately the phone rang. Then I sat on hold for 2 hours waiting to be connected. After that, I gave up and hung up. Immediately the phone rang again, but then told me that I had called Apple outside of business hours and hung up. I am a first time submitter, and have all kinds of questions about the submission process. If I did something wrong, please tell me so I can fix it. But leaving me in the queue for a week is just mean. Can I get a review, please?

My app has been waiting for review since June 13 and has been under review since June 19. I would like to know if this is considered normal. I have already sent emails to Apple requesting a faster review and asking for an explanation regarding the delay, but I have not received a helpful response. The app is called "Piscineiros." Could any fellow developers please check if this review timeline is normal or share if you've experienced something similar? Any advice would be greatly appreciated.

Hello, My app MGY Fit (Apple ID: 6793196121, iOS, version 1.0.0, build 11) was submitted for review on July 23, 2026 and has remained in "Waiting for Review" ever since. It has never moved to "In Review". There are no messages in the Resolution Center and I have not received any request for additional information. Export compliance, content rights, and advertising identifier questions were all answered at submission, and the Review Notes include demo account credentials and steps to reach the main flows. This is the first submission for this app and for my developer account, so I understand a longer wait is expected. I wanted to check whether the submission may have been routed in a way that needs attention, or whether this is simply current queue volume. Any guidance would be appreciated. Thank you.

Hello Apple Developer Community and App Review Team, I received a Pending Termination Notice regarding Section 4.3 (Spam) for my games (Scream Bird and Hopscotch). I submitted a formal appeal 7 days ago detailing the technical context, but I have not yet received an automated confirmation email or a case tracking number. Full Context of My Situation: I had previously published a game called "Scream Bird" on this account, and that was the first time I received a 4.3 Spam error. It was the first time I'd encountered this error, as all my games and applications are designed by me, from the buttons to the characters and gameplay. When I received that error, I tried to understand and modify my game a bit, thinking it might have overlapped with an existing game. But that build continued to receive the 4.3 Spam error. This time, I really didn't know what to do. I intended to keep the gameplay but redesign everything. Strangely, while I was trying to redesign and change my game, I received an email saying that Apple was reviewing my app (the one that had just been rejected), and just minutes later, my game was approved and ready for distribution. This was the first time I'd encountered something like this. I thought the review team had re-evaluated my game and changed their minds. And since the game was approved, I didn't know what else to do and just continued working on other projects. Shortly after, Google AdMob approved it (because the game was already live on the store), so ads started appearing on the game (I think this was the issue, causing the system to automatically think my game had been flagged for content changes, but the content was already there; it was just that I had set a production ID for the ads at the time, so they weren't showing – that was partly my fault). But the problems didn't end there. Recently, I published a new game called "Hopscotch" and encountered the 4.3 Spam issue again. It was then that I really looked back at the binary files I built for my games and was shocked to realize that this might be the reason the automated system incorrectly flagged my games as spam. Technical Explanation (Godot Framework & Shared Native Libraries): I build all my games myself using Godot (3.x and 4.x). Regardless of the version, I write supporting libraries (mainly to call simple native features). Therefore, all my games will have files like: notch.a, share.a, haptics.a, local-notification.a, inappstore.a... You can check it out on my GitHub page; most of it is public. https://github.com/kyoz/godot-notch https://github.com/kyoz/godot-share https://github.com/kyoz/godot-local-notification https://github.com/kyoz/godot-haptics https://github.com/kyoz/godot-leaderboard https://github.com/kyoz/godot-native-rating https://github.com/kyoz/godot-flashlight etc... However, the entire game, from images, models, scenes... almost everything I designed myself, was packed into a single [game].pck file by Godot. This makes my Godot-built games look very similar in terms of binary, but in terms of content and gameplay, they are completely unrelated. My Commitment: I've been on my Apple journey for over five years now, and I've published 20 apps/games. The journey so far hasn't been easy. But I promise I've always complied with Apple's policies. I have never engaged in subscription scams, fake reviews, bait-and-switch tactics, or any of the fraudulent conduct described in the termination notice. I am respectfully requesting: Confirmation if my appeal submitted 7 days ago is actively under review by the App Review Board. A status update or Case Reference Number for tracking. I am fully cooperative and ready to provide full source code, Godot project files, or any documentation needed. Thank you so much for your time and assistance! Best regards, Phan Minh Cuong

Hi, I feel like there's been some miscomunnication with the app review team. I have been replying to the rejection and re-submitting and my comments don't seem to be read and I get the same rejection parroted out with not much clue about which action I really need to take as it's quite vague. Does the App Review team reply to the rejection without me having to re-submit? Maybe I'm just not being patient enough or I'm using the submission process wrong.

I paid the $99 annual Apple Developer Program fee and submitted my first iOS app with the understanding that App Review would normally take approximately one or two days. It has now been six days, and the submission is still sitting in “Waiting for Review.” There has been no review, no request for additional information, no explanation, and no indication that anyone has looked at it. I understand that review times can vary, especially for a first submission, but six days without even entering review seems excessive. Developers are required to pay Apple before they can distribute an app, yet there appears to be no meaningful service-time commitment or communication when a submission remains untouched. Is this currently normal for first-time app submissions? At what point is a developer supposed to conclude that the submission is stuck rather than merely delayed? At this point, I am also wondering whether I should request a refund of the $99 membership fee, since the primary service I paid to access has not been provided within anything resembling the expected timeframe.

Subject: Request for Account-Level Investigation – Multiple App Review Delays and Apple Search Ads Not Delivering Hello Apple Developer Support, I am requesting an account-level investigation because I am experiencing multiple issues on the same Apple Developer account at the same time, and despite contacting support several times, I have not received any response. Issue 1 – Unusually Long App Review Delays I currently have two different apps experiencing unusually long review times. One app update has been waiting significantly longer than expected. Another app has been stuck in In Review for approximately one week with no communication or status change. I understand that review times can vary, but having multiple submissions delayed simultaneously is highly unusual compared to my previous submissions. Issue 2 – Apple Search Ads Not Delivering At the same time, my Apple Search Ads campaigns are not delivering at all. Current status: Campaigns are Enabled Ad Groups are Enabled Keywords are Enabled Billing is valid Payment method is active Promotional credit is available My app is live on the App Store Search Match configuration has been verified Campaigns have been running for several days However, every campaign reports: 0 Impressions 0 Taps 0 Spend I have already verified my campaign configuration multiple times and exported the campaign data. Everything appears to be configured correctly, yet the campaigns have never entered auction or delivered any impressions. Additional Information My app is already indexed in App Store Search, and third-party ASO tools show that keyword rankings are updating, which indicates that the app is searchable. However, Apple Search Ads still records zero delivery across all campaigns. What I Have Already Done Verified campaign settings Verified keyword status Verified billing information Verified payment method Verified app availability Contacted Apple Developer Support multiple times via email Waited several days without any response Request Could you please investigate whether there is any account-level, App Review, or Apple Search Ads restriction affecting my developer account? If this case needs to be handled by another internal team (App Review or Apple Search Ads), I kindly ask that it be escalated internally rather than requiring me to open separate cases. I would greatly appreciate confirmation that my developer account is in good standing and that there are no internal issues preventing: My apps from progressing through App Review. My Apple Search Ads campaigns from delivering impressions. Thank you for your time. I look forward to your assistance and would appreciate any update regarding this investigation. Kind regards, Hilal Demir Apple Developer Program Member

Hello everyone, I’m looking for advice from developers who may have faced a similar situation, as we appear to be stuck in a long-running loop of Guideline 4.3(a) rejections on iOS with no actionable feedback from App Review. Over an extended period, our iOS app has been repeatedly rejected under Guideline 4.3(a) (“similar or repackaged”), regardless of the changes we make. The responses from App Review consistently use the same high-level language and do not indicate what specifically is considered problematic. Some relevant context: The app is built with Flutter using a single shared codebase. The macOS version, built from the same codebase with the same overall structure and UI, has been approved without issues. The iOS version, using that same implementation, continues to receive 4.3(a) rejections. We do not use purchased templates and do not operate multiple developer accounts. Like most apps, we use some third-party and open-source components where technically appropriate. Across multiple submissions, we have tried to address the feedback as best we can by making changes to UI/UX, assets, metadata, internal structure, and overall product quality. However, App Review has not provided clarification even at a high level (for example, whether the concern is primarily related to UI/UX, code structure, metadata, user flows, or overall product framing). Requests for any directional guidance have resulted in the same generic responses, both in review replies and via support. This leaves us making blind changes without a feedback loop. As a result, it’s difficult to understand whether the issue is realistically correctable, or whether the app is effectively blocked due to similarity clustering or other non-obvious review heuristics. Any firsthand experiences, practical steps, or lessons learned would be extremely helpful.

Hi, I have a submission (App Store Connect ID: 6754396289) that has been stuck in "InReview" status for almost 3 months now. I tried with support multiple time but always received a generic reply. I am experiencing ususually long delay and would Appreciate any guidance from Apple Review or other developers. Can the Apple Review team check why submission iD:6754396289 is Stuck in "InReview" status and what information is needed to move it forward?

Hi, I'm completely blocked from TestFlight. Every attempt returns: "status": "422", "code": "BETA_CONTRACT_MISSING", "title": "Beta contract is missing for the app." This is an older account that has used TestFlight fine before. Nothing changed on my end, no account changes, no agreement updates. What I've already checked: Business > Agreements: Paid Apps and Free Apps both Active Tax forms and bank account Active No pending banners anywhere in App Store Connect or developer.apple.com Test Information complete Export compliance answered Build processes to VALID with no warnings Same error on a brand new app with a fresh build, so it looks like the beta contract is detached on the backend rather than an app-level problem. I've filed a support request and haven't heard back. This is time sensitive, I have a client pilot waiting on an external TestFlight link. Is there any way to get this re-provisioned? Apple Support case ID: 20000118605424 Thanks.

My app with ID 6755565836 is waiting for review with 0 updates and replies to my contact attempts through developer contact us for 15 days and counting. Is this the new normal now? Is there anything that I can do to make sure it will actually get reviewed in the end? I am concerned if someone just put it somewhere and forgot about it and I am waiting for nothing. Please assist.

Hello, Our app, Platform Kiralama Rehberi, has been repeatedly rejected under Guideline 4.2 – Minimum Functionality, even though we have made substantial improvements after every review. We fully respect the App Review process. However, we strongly believe that the current version of our app provides sufficient functionality and meaningful value for its intended audience. Despite adding new features, expanding the content, and redesigning the user experience, we continue to receive almost the same general response without a specific explanation of what is still considered insufficient. The app is specifically developed for professionals and users in the manlift industry in Türkiye. It currently includes: A location-based interactive map showing nearby companies Distance calculations based on the user’s location Rental, manufacturer, distributor, spare parts, and technical service categories City and category-based filtering Detailed company pages with contact, address, and location information A searchable database of approximately 350–400 machine fault codes Favorites for companies, fault codes, and technical documents A technical and safety document library Native navigation between map pins, company cards, and detail pages After each rejection, we carefully reviewed the feedback and continued improving the app. We believe the app is no longer a simple catalogue or content viewer. It offers several interactive, practical, and location-based features designed for a specific professional sector. Our main concern is that the app may not have been fully explored during review, as the responses we receive remain almost identical despite the significant changes between submissions. We respectfully request that the app be reviewed again in detail, preferably by a different reviewer or App Review team member, so that all of its current features can be tested fairly and completely. We are confident in the usefulness and functionality of the app. We are not trying to avoid further development, but without specific feedback, it is becoming difficult to understand what additional functionality is genuinely expected. Could someone please advise us on the most appropriate next step, or help ensure that the app receives a fresh and detailed review? NOTE: For nearly two months, we have made extensive improvements to the app in an effort to move past this stage. During this process, we have tried to contact Apple Developer Support and have also communicated directly with the reviewer. However, the reviewer continues to send nearly the same response regarding Guideline 4.2, while we have received no response from the Support team for approximately 10 days. For this reason, we genuinely need the app to be reviewed in detail by a different reviewer and to receive clear, specific guidance on what is still considered insufficient. Thank you.

My app was rejected July 16 under Guideline 2.1 (Information Needed) with four questions about the Clinical Health Records API. I replied in full the same day in the Resolution Center, and followed up in that thread on July 22. It has now been 12 days with no response from App Review. I have also contacted Developer Support (case 102942988807), which replied twice but could not provide status on the submission. I have not clicked Resubmit, since Apple's message asked me to reply, and I understand resubmitting closes the correspondence thread. Is there anything further I should be doing, or is a reply alone sufficient to return the submission to the review queue? Submission ID: bc855e56-3ef8-482d-96b0-4380d3fc4a68

My first app submission has been in "Waiting for Review" for nine days and has not yet entered review. App: Shotaway — Screenshot Cleaner App ID: 6789611184 Version: 1.0 (build 1.0.0 (7)) Submission ID: e8b8c4ea-6107-4688-a630-102479bfd5d4 Submitted: July 19, 2026, 5:52 PM KST Platform: iOS Current status: Waiting for Review Four other submissions from the same account are also still waiting: Warmthly: Keep in Touch 6789600652 submitted July 23 Fanspot: K-Pop Fan Map & Cafes 6789989805 submitted July 24 Stampic: Travel Photo Map 6789523290 submitted July 24 NanaFrame: Family Photo Widget 6790092570 submitted July 25 I checked the Contact the App Review Team form, but none of the available topics match a status question, so I am posting here instead. Since all of these were prepared the same way, I am wondering whether I made a mistake that applies to all of them. If there is missing or incomplete information on my side, I would like to correct it. I am not requesting an expedited review. I only want to know whether something on my end is blocking these submissions. Thank you.

YouTube music isn't playing in the background as it should be; it’s playing on screen even once you’ve paid for the subscription. The app just floats in the background of whats on your active phone screen.

Hi everyone, I submitted an update to my existing app. The app has been in "Waiting for Review" for over 6 days, and it hasn't moved to the "In Review" stage yet. This is not a new app submission—it's an update to an existing app that has already been approved previously. Has anyone else experienced similar delays recently? Is this within the normal review timeline, or is there anything I should do besides waiting? I've already contacted Apple Developer Support to ask about the status. Any recent experiences or suggestions would be appreciated. Thanks!

Hi everyone, We recently renewed and successfully paid for our Apple Developer Program membership. However, our account is still showing as expired, and we're unable to access the developer services that require an active membership. We've already completed the payment, but the membership status has not updated yet. Has anyone experienced this issue before? How long did it take for your membership to become active after payment? Is there anything we need to do, or is this just a delay on Apple's side? Should we contact Apple Developer Support, or will the status update automatically? Any advice would be greatly appreciated. Thank you!